nginx: add entry for /api, use client_max_body_size #1924
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
backport-4.2
himdel
removed
backport-4.2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running oci-env, I can not upload some collections, because the upload size limit is too small.
On actual galaxy.ansible.com, this is 20M, but the oci-env config uses a 10M default, only overriding it for
/pulp/api/v3/(in https://github.com/pulp/pulp-oci-images/blob/latest/images/s6_assets/nginx.conf#L62).Our api calls go to
/api/automation-hub/,/api/galaxy/or/api/so thatclient_max_body_size 0;doesn't apply.I'm assuming this is something to fix in galaxy_ng, as those URLs are galaxy-specific, is that right?
(=> added an
/api/entry in the galaxy_ng nginx snippet, copied from/pulp/api/v3inpulp-oci-images)Testing: try uploading arista.avd 4.2.0 from the UI.